-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include versions and checksums in VMR publishing and remove prepare-artifacts.proj #100004
Conversation
d769d5e
to
3533944
Compare
3533944
to
3e78558
Compare
@@ -8,7 +8,7 @@ | |||
|
|||
<PropertyGroup> | |||
<IncrementalNativeBuild Condition="'$(IncrementalNativeBuild)' == ''">true</IncrementalNativeBuild> | |||
<BuildCoreHostDependsOn>GetProductVersions;GenerateRuntimeVersionFile</BuildCoreHostDependsOn> | |||
<BuildCoreHostDependsOn>GenerateRuntimeVersionFile</BuildCoreHostDependsOn> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I checked and I couldn't find a place under src/native that still depended on the GetProductVersions
target.
<Target Name="_SetProductVersion" DependsOnTargets="GetProductVersions" BeforeTargets="Pack"> | ||
<PropertyGroup> | ||
<PackageVersion>$(ProductVersion)</PackageVersion> | ||
</PropertyGroup> | ||
</Target> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From what I could see, this setting shouldn't be necessary as PackageVersion is already automatically set by Arcade.
<ItemGroup> | ||
<_MonoRollupEnvironmentVariable Include="Configuration:$(Configuration)" /> | ||
<_MonoRollupEnvironmentVariable Include="NativeBinDir:$(NativeBinDir)" /> | ||
<_MonoRollupEnvironmentVariable Include="WasmObjDir:$(WasmObjDir)" /> | ||
<_MonoRollupEnvironmentVariable Include="ProductVersion:$(ProductVersion)" /> | ||
<_MonoRollupEnvironmentVariable Include="ProductVersion:$(RuntimePackProductVersion)" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Calling into sfxproj to retrieve the version felt safer than just relying on PackageVersion here in case this project sets IsShipping or any other properties already or in the future.
@@ -37,7 +37,6 @@ | |||
<Target Name="SetupTestContextVariables" | |||
Condition="'$(IsTestProject)' == 'true'" | |||
DependsOnTargets=" | |||
GetProductVersions; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I couldn't find any place that still depends on this target or its properties.
<Target Name="SetTargetBasedPackageVersion" | ||
BeforeTargets="GenerateNuSpec" | ||
DependsOnTargets="GetProductVersions"> | ||
<PropertyGroup> | ||
<Version>$(ProductVersion)</Version> | ||
<!-- | ||
PackageVersion is normally calculated using Version during static property evaluation, but | ||
we need some info from GetProductVersions, so it's too late to rely on that. We need to set | ||
both in target evaluation, here. | ||
--> | ||
<PackageVersion>$(ProductVersion)</PackageVersion> | ||
</PropertyGroup> | ||
</Target> | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might have been necessary in the past but AFAIK, NuGet calculates PackageVersion correctly, even for pkgprojs.
… into ViktorHofer-patch-1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes LGTM pending a clean official build and VMR build
Fixes dotnet/source-build#4239 Replaces dotnet#100004 Co-authored By: Viktor Hofer <[email protected]>
* Unify dotnet/runtime on using Arcade -publish Fixes dotnet/source-build#4239 Replaces #100004 Co-authored By: Viktor Hofer <[email protected]> * Use DotNetBuildOrchestrator to avoid executing in a repo source-build context. * Actually, we want this logic to run only when we're running in a non-VMR-like context, even repo build. * Restore, but only restore the toolset in the publish job * Fix Exists check and do the "restore toolset only" check one degree away from the Arcade SDK. * Set the "publish using pipelines" global property when publishing * Don't produce the product version files on repo source build.
Fixes dotnet/source-build#4239
Follows the pattern that we established in windowsdesktop: https://github.com/dotnet/windowsdesktop/blob/main/eng/Publishing.props
Important: No Merge until I verified the changes in a runtime official build and a VMR build.
Runtime official build: https://dnceng.visualstudio.com/internal/_build/results?buildId=2414748&view=results